Skip to content

Commit db0ccee

Browse files
authored
feat: asset type explorer upgrade (#68)
1 parent 4587702 commit db0ccee

File tree

9 files changed

+65
-27
lines changed

9 files changed

+65
-27
lines changed
103 KB
Loading
-57.5 KB
Loading
Binary file not shown.

src/get-started/tooling-and-explorers/iexec-explorer.md

Lines changed: 35 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -114,13 +114,6 @@ Browse and analyze all tasks across the iExec network:
114114

115115
### Task Execution Monitoring
116116

117-
<ImageViewer
118-
:image-url-dark="taskDetailsStartedImage"
119-
image-alt="Result Decryption"
120-
:link-url="`${explorerUrl}/tasks`"
121-
caption="Explore Tasks"
122-
/>
123-
124117
<ImageViewer
125118
:image-url-dark="taskDetailsCompletedImage"
126119
image-alt="Task Completed"
@@ -154,7 +147,7 @@ Browse and analyze all tasks across the iExec network:
154147
:image-url-dark="appViewImage"
155148
image-alt="App View"
156149
:link-url="`${explorerUrl}/apps`"
157-
caption="Explore iApp Marketplace"
150+
caption="Explore iApp"
158151
/>
159152

160153
Explore the iExec application marketplace:
@@ -169,24 +162,50 @@ Explore the iExec application marketplace:
169162
:image-url-dark="datasetViewImage"
170163
image-alt="Dataset View"
171164
:link-url="`${explorerUrl}/datasets`"
172-
caption="Explore Protected Datasets"
165+
caption="Explore Protected Data"
173166
/>
174167

175168
Navigate the protected data landscape:
176169

177-
- **Data Catalog**: Discover available datasets with their metadata and asset
178-
type
179-
- **Usage Patterns**: Analyze dataset popularity and user adoption
180-
- **Schema Validation**: Ensure data structure compatibility with your
181-
applications
170+
- **Data Catalog**: Discover available protected data with their metadata and
171+
asset types
172+
- **Usage Analytics**: Analyze protected data popularity and adoption trends
173+
across the network
174+
- **Schema Discovery**: Find protected data that matches your requirements using
175+
advanced filtering
176+
177+
The explorer provides a powerful filtering system that lets you search for
178+
protected data based on their schema structure, making it easy to find datasets
179+
compatible with your iApp.
180+
181+
<ImageViewer
182+
:image-url-dark="assetTypesAdvanceFilterViewImage"
183+
image-alt="asset Types Advance Filter View"
184+
:link-url="`${explorerUrl}/datasets`"
185+
caption="Explore Asset Types Filter"
186+
/>
187+
188+
**How to use the asset type filter:**
189+
190+
1. **Select asset type criteria** - Choose from predefined types and enter the
191+
field names
192+
2. **Apply multiple filters** - Combine asset type filters with other criteria
193+
like date range, owner, or tags
194+
3. **Browse matching datasets** - View only the protected data that matches your
195+
schema requirements
196+
197+
This filtering capability is essential when building iApps that need specific
198+
data structures. For example, if your iApp processes user profiles, you can
199+
filter for datasets containing `email: string` and `age: f64` fields to ensure
200+
compatibility.
182201

183202
## Workerpools
184203

185204
<ImageViewer
186205
:image-url-dark="workerpoolViewImage"
187206
image-alt="Workerpool View"
188207
:link-url="`${explorerUrl}/workerpools`"
189-
caption="Explore Workerpools Infrastructure"
208+
caption="Explore Workerpools"
190209
/>
191210

192211
Explore the decentralized computing infrastructure:
@@ -216,9 +235,9 @@ const explorerUrl = computed(() => chainData.value.iexecExplorerUrl);
216235
import explorerGlobalImage from '@/assets/tooling-&-explorers/iexec-explorer/explorer-global.png';
217236
import dealViewImage from '@/assets/tooling-&-explorers/iexec-explorer/deal-view.png';
218237
import taskViewImage from '@/assets/tooling-&-explorers/iexec-explorer/task-view.png';
219-
import taskDetailsStartedImage from '@/assets/tooling-&-explorers/iexec-explorer/task-details-started.png';
220238
import taskDetailsCompletedImage from '@/assets/tooling-&-explorers/iexec-explorer/task-details-completed.png';
221239
import appViewImage from '@/assets/tooling-&-explorers/iexec-explorer/app-view.png';
222240
import datasetViewImage from '@/assets/tooling-&-explorers/iexec-explorer/dataset-view.png';
223241
import workerpoolViewImage from '@/assets/tooling-&-explorers/iexec-explorer/workerpool-view.png';
242+
import assetTypesAdvanceFilterViewImage from '@/assets/tooling-&-explorers/iexec-explorer/asset-types-advance-filter.png';
224243
</script>

src/guides/build-iapp/inputs.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -413,7 +413,8 @@ Add your App Secret to the project configuration:
413413

414414
### How to Access App Secrets
415415

416-
App secrets are exposed as environment variables following the `IEXEC_APP_DEVELOPER_SECRET` naming pattern.
416+
App secrets are exposed as environment variables following the
417+
`IEXEC_APP_DEVELOPER_SECRET` naming pattern.
417418

418419
::: code-group
419420

src/guides/manage-data/handle-schemas-dataset-types.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,11 @@ Think of schemas as **data fingerprints** - they tell iApp "this protected data
1616
contains an email address and a phone number" without revealing the actual
1717
values.
1818

19+
Use the
20+
<a :href="`${explorerUrl}/datasets`" target="_blank" rel="noopener">iExec
21+
explorer</a> to browse protected data and see their asset types. Make filtered
22+
searches based on schema to find data that fits your needs.
23+
1924
## How schemas work
2025

2126
When you protect data with DataProtector, the SDK automatically analyzes your
@@ -131,6 +136,10 @@ const listProtectedData = await dataProtectorCore.getProtectedData({
131136

132137
## Real examples
133138

139+
For real-world applications built by developers using various asset types, check
140+
out the [iExec case studies](https://www.iex.ec/case-studies) to see how schemas
141+
are used in production environments.
142+
134143
### Simple User Profile
135144

136145
```ts twoslash
@@ -269,3 +278,17 @@ explore next:
269278
for running computations
270279
- **See it in action**: Try our [Hello World tutorial](/get-started/helloWorld)
271280
for a complete example
281+
282+
<script setup>
283+
import { computed } from 'vue';
284+
import useUserStore from '@/stores/useUser.store';
285+
import {getChainById} from '@/utils/chain.utils';
286+
import ImageViewer from '@/components/ImageViewer.vue';
287+
288+
// Get current chain info
289+
const userStore = useUserStore();
290+
const selectedChain = computed(() => userStore.getCurrentChainId());
291+
292+
const chainData = computed(() => getChainById(selectedChain.value));
293+
const explorerUrl = computed(() => chainData.value.iexecExplorerUrl);
294+
</script>

src/references/dataProtector/dataProtectorCore/processProtectedData.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -208,8 +208,7 @@ const processProtectedDataResponse =
208208

209209
Do not use this to provide any sensitive information to the application. All
210210
arguments passed this way are visible in plain text using the
211-
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
212-
explorer</a> .
211+
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
213212

214213
:::
215214

@@ -448,8 +447,7 @@ import { type ProcessProtectedDataResponse } from '@iexec/dataprotector';
448447

449448
The ID of the transaction that happened on iExec's side chain. You may view
450449
details on the transaction using the
451-
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
452-
explorer</a> .
450+
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
453451

454452
### dealId
455453

@@ -463,8 +461,7 @@ Identifies the specific deal associated with this transaction.
463461

464462
A unique identifier associated with a task currently running on the iExec
465463
protocol. You can monitor task execution using the
466-
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
467-
explorer</a> .
464+
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
468465

469466
::: tip
470467

src/references/web3mail/methods/sendEmail.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -313,8 +313,7 @@ import { type SendEmailResponse } from '@iexec/web3mail';
313313

314314
This uniquely identifies the email task on the iExec side chain. You can view
315315
the status of the `sendEmail` method by monitoring the task on the
316-
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
317-
explorer</a> .
316+
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
318317

319318
## Error Handling
320319

src/references/web3telegram/methods/sendTelegram.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -281,8 +281,7 @@ import { type SendTelegramResponse } from '@iexec/web3telegram';
281281

282282
This uniquely identifies the telegram task on the iExec side chain. You can view
283283
the status of the `sendTelegram` method by monitoring the task on the
284-
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
285-
explorer</a> .
284+
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
286285

287286
<script setup>
288287
import { computed } from 'vue';

0 commit comments

Comments
 (0)