Repository navigation
fix: the asset link picker searches like the catalog and only offers the types the field accepts - #88
Merged
Merged
Conversation
…the types the field accepts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Picking the target of a link field (
control: asset) usedGET /assets/search, a different search from the one in the header: typing «área de gobierno 2» returned anything with «gobierno» in it and not the area, because it neither folds accents nor ranks by name, and it ignored the field'stargetAssetTypes.findAssetsnow asksGET /search?types=asset, the catalog search, and resolves the hits through/assets/refs.targetAssetTypesasgoverned.asset_type, so «Parent area» only offers lines of business.Prettier and ESLint pass. Not exercised in a browser against a real catalog.