Hiding internal files.

[plasmLC]

Guys, is this possible? My app provides advanced access to the /Dcouments application folder, and Realm, for example, allows to choose which file name should be used. SwiftyBeaver uses file names without leading dot, so it will be visible for app's users.

What do you suggest to hide your files from user's eyes?

[skreutzberger]

What files do you mean and for what destination?

[plasmLC]

/Documents/sbplatform_analytics.json
/Documents/sbplatform_entries_sending.json

As I said before, my app provides access to the /Documents folder directly to users, so it very unlikely to show these files.

[skreutzberger]

Ah ok, I understand what you mean. You want to change the values of the 3 files at https://github.com/SwiftyBeaver/SwiftyBeaver/blob/master/sources/SBPlatformDestination.swift#L71

I will put it on the list for the next release to make these variables public / open (for Swift 3). In the meantime you can manually get access to these variables by making the public in the framework codebase.

[plasmLC]

@skreutzberger sorry, but I could not manage it to work properly.

I'm doing this:

But one file - sbplatform_analitycs.json will be created in any case.
I suppose it will be there until behaviour of initialization will be changed: see from line 131 to line 147.

You're working with default names ANYWAY, so, please, do something with this. Either add leading dot before filenames or let user really change this urls and stop using default names before user changed it.

Guys, really need this fix — I could not allow my users see 'system' stuff among their documents.

[plasmLC]

@skreutzberger I suppose I need to fork the repo and do it on my own? Will you fix this?

[skreutzberger]

@plasmLC A solution could be to add the file names as additional parameters to init() but that may confuse users 🤔

[plasmLC]

@skreutzberger even if this init() will be convenience?

[skreutzberger]

let me do a PR and then you can see if you like it :)

[skreutzberger]

@plasmLC please see here: #184 - would that solve your issue?

[plasmLC]

@skreutzberger yes, exactly what I need!

[skreutzberger]

@plasmLC Thanks! I will merge it into master and it will ship with the next version 1.1.3 later this week.