bulky | rename files | File Utils library

IIUC, use value_counts:

There is a new pseudo-class :is which will allow this..

The :is() CSS pseudo-class function takes a selector list as its argument, and selects any element that can be selected by one of the selectors in that list.

This is actually not true:

@Composable functions don't have return values.

You can annotate both function with return types and even getter only properties with @Composable. For example this is part of Material theme source code.

Here's how you can define your color:

I solved it myself. The reason for the long wait was that the value we were looking for did not exist, so the test failed. I can set the length in the cypress.json file:

First Some Background

Synapse stores all artifacts in JSON format. In the Git repo, they are in the following folder structure:

Inside each folder are the JSON files that define the artifacts. Folder sqlscript contains the JSON for SQL Scripts in the following format:

NOTE: the Synapse folder of the script is just a property - this is why all SQL Script names have to be unique across the entire workspace.

Extracting the script

The workspace does allow you to Export SQL to a .sql file:

There are drawbacks: you have to do it manually, 1 file at a time, and you cannot control the output location or SQL file name.

To pull the SQL back out of the JSON, you have to access the properties.content.query property value and save it as a .sql file. As far as I know, there is no built in feature to automatically save a Script as SQL. Simple Copy/Paste doesn't really work because of the \ns.

I think you could automate at least part of this with an Azure DevOps Pipeline (or a GitHub Action). You might need to copy the JSON file out to another location, and then have a process (Data Factory, Azure Function, Logic App, etc.) read the file and extract the query.

The useParams hook can only access the route match params of a Route within the context of the Routes component rendering it. App is outside the Routes component that renders a route rendering path='/palette/:id'.

You can create a wrapper component to "sip" the id route match param and do the filtering.

Here's an example of how to do this using a lookup table. You can hardcode it or build it from code if the structure allows it.

I tested this with a few folders setting up different ACLs with my own user and it seem to be working but I haven't tested enough to be sure. Basically, the script will loop through directories and add the ACLs to a dictionary where the Keys are each IdentityReference and the Values are the properties from the ACLs which you're interested on (FileSystemRights and AccessControlType) in addition to the folder's absolute path. While enumerating the directories, each object will be compared against the stored values using the Compare-Acl function which only returns $true if the object is different.

When I listen to a collection that contains a few (hundreds) documents, the listener works fine.

That's the expected behavior.

However when the collection starts getting bulky (over 30-40k), it never triggers the callback.

That's also the expected behavior since reading that amount of data takes a long long time. Besides that, it's also very costly, since everything in Firestore it's about the number of reads and writes you perform.

Reading 30-40k documents at once can be considered an enormous amount of data. Besides that, I don't think that somebody will ever be interested in reading all that data. So the best option that you have is to limit the number of documents your read.

Besides that, the most common approach would be to always read the exact number of documents that you display on the screen. That being said, you should consider getting data in smaller chunks. Most likely 10-20 documents. You can also consider implementing pagination if your app's use case requires it.