Skip to content

Conversation

@appurist
Copy link
Contributor

My intention with this fork was for it to be specific to InWorldz but it does provide good examples of how to whitelist objects independent of the normal (owner+creator) concerns for whitelist in load filtered. I've decided we should probably merge this into master since it really the only IW-specific code there is the IsWhitelistedObject function, but this code should be completely harmless and demonstrates where to insert such exception cases in any future filtering.

However, if it is felt that this branch should not be merged, then there are two commits with a straight fixes for the master, the bottom two: bac40ba and c62e15b which can either be cherrypicked or I can do another branch which only has those two commits.

This is a specific change for InWorldz exports to avoid filtering out LiteRezzer scripts from any objects grid-wide without whitelisting a creator user. Not sure if this belongs in Halcyon itself or is just an IW feature, but it's being used in all export OARs now.
InWorldz-specific changes for OAR exports, although the pattern could be used in general.
Not found due to the fact that all assets are loaded and not filtered until objects are filtered since assets don't have creator metadata.
@kf6kjg
Copy link
Contributor

kf6kjg commented Apr 21, 2021

I think we'd discussed this out of band way back when... To document my current thoughts on this PR: I'd rather that either the PR be split into the bugfix portion and a PR working toward generalizing the whitelisting code, or that the whitelisting be generalized in this PR. Either way, this PR as it stands introduces technical debt that will have to be cleaned up by someone anyway - and we have enough such debt IMO.

Copy link
Contributor

@kf6kjg kf6kjg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above about either splitting off the bug fix portion or generalizing the whitelisting process.

@kf6kjg kf6kjg force-pushed the master branch 4 times, most recently from 5855a6f to 3276883 Compare June 7, 2021 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants