Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support "mapped" flag for StudioOpenDialog in isfs filters and export #931

Closed
isc-tleavitt opened this issue Apr 15, 2022 · 0 comments · Fixed by #932
Closed

Support "mapped" flag for StudioOpenDialog in isfs filters and export #931

isc-tleavitt opened this issue Apr 15, 2022 · 0 comments · Fixed by #932
Labels
enhancement New feature or request

Comments

@isc-tleavitt
Copy link

isc-tleavitt commented Apr 15, 2022

Use case:
I want to connect to an interoperability-enabled namespace using isfs, and to export everything from it to my local filesystem. I don't want InterSystems' code to be included - e.g., the CSPX, Ens*, HS*, and SchemaMap packages. The defining characteristic of these is that they are mapped from non-default routine DBs for the namespace.

Fortunately, %Library.RoutineMgr:StudioOpenDialog has a "Mapped" option which defaults to 1 but can be set to 0 to omit these classes. We should support "mapped=false" as a URL parameter and export config option to support omitting mapped classes from both isfs views and export. (This could be two separate issues, but I think it makes more sense as a single issue to support a systemic review of all places where this flag might be relevant.)

@isc-tleavitt isc-tleavitt changed the title Support Support "mapped" flag for StudioOpenDialog in isfs filters and export Apr 15, 2022
@isc-bsaviano isc-bsaviano added the enhancement New feature or request label Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants